You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
pnpm self-update should not leave a directory with a broken pnpm installation if the installation fails.
Allow scope registry CLI option without --config. prefix such as --@​scope:registry=https://scope.example.com/npm#9089.
pnpm self-update should not read the pnpm settings from the package.json file in the current working directory.
pnpm update -i should list only packages that have newer versions #9206.
Fix a bug causing entries in the catalogs section of the pnpm-lock.yaml file to be removed when dedupe-peer-dependents=false on a filtered install. #9112
Fixed the Regex used to find the package manifest during packing #8938.
pnpm update --filter <pattern> --latest <pkg> should only change the specified package for the specified workspace, when dedupe-peer-dependents is set to true#8877.
Fixed publish/pack error with workspace dependencies with relative paths #8904. It was broken in v9.4.0 (398472c).
Use double quotes in the command suggestion by pnpm patch on Windows #7546.
Do not fall back to SSH, when resolving a git-hosted package if git ls-remote works via HTTPS #8906.
Improve how packages with blocked lifecycle scripts are reported during installation. Always print the list of ignored scripts at the end of the output. Include a hint about how to allow the execution of those packages.
Metadata directory version bumped to force fresh cache after we shipped a fix to the metadata write function. This change is backward compatible as install doesn't require a metadata cache.
Patch Changes
pnpm update --global should not crash if there are no any global packages installed #7898.
Fix an exception when running pnpm update --interactive if catalogs are used.
Platinum Sponsors
Gold Sponsors
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
If you want to rebase/retry this PR, check this box
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually
The artifact failure details are included below:
File name: undefined
Command failed: corepack use pnpm@9.15.9
(node:2234) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
(Use `node --trace-deprecation ...` to show where the warning was created)
ERROR [sentry-rollup-plugin] Warning: No auth token provided. Will not create release. Please set the authToken option. You can find information on how to generate a Sentry auth token here: https://docs.sentry.io/api/auth/
ERROR [sentry-rollup-plugin] Warning: No auth token provided. Will not upload source maps. Please set the authToken option. You can find information on how to generate a Sentry auth token here: https://docs.sentry.io/api/auth/
ERROR Cannot read properties of undefined (reading 'replace')
at node_modules/.pnpm/unstorage@1.14.4_@netlify+blobs@8.1.0_aws4fetch@1.0.20_db0@0.2.1_ioredis@5.4.2/node_modules/unstorage/drivers/s3.mjs:34:39
at createStorage (node_modules/.pnpm/nitropack@2.10.4_@netlify+blobs@8.1.0_aws4fetch@1.0.20_typescript@5.7.2/node_modules/nitropack/dist/core/index.mjs:1038:27)
at async createNitro (node_modules/.pnpm/nitropack@2.10.4_@netlify+blobs@8.1.0_aws4fetch@1.0.20_typescript@5.7.2/node_modules/nitropack/dist/core/index.mjs:1077:19)
at async initNitro (node_modules/.pnpm/nuxt@3.15.1_@netlify+blobs@8.1.0_aws4fetch@1.0.20_eslint@9.17.0_rollup@4.30.0_tsx@4.19.2_type_c2oic35tufqgfjkhcuvduauulq/node_modules/nuxt/dist/shared/nuxt.C9wc04RR.mjs:4101:17)
at async initNuxt (node_modules/.pnpm/nuxt@3.15.1_@netlify+blobs@8.1.0_aws4fetch@1.0.20_eslint@9.17.0_rollup@4.30.0_tsx@4.19.2_type_c2oic35tufqgfjkhcuvduauulq/node_modules/nuxt/dist/shared/nuxt.C9wc04RR.mjs:5384:3)
at async loadNuxt (node_modules/.pnpm/nuxt@3.15.1_@netlify+blobs@8.1.0_aws4fetch@1.0.20_eslint@9.17.0_rollup@4.30.0_tsx@4.19.2_type_c2oic35tufqgfjkhcuvduauulq/node_modules/nuxt/dist/shared/nuxt.C9wc04RR.mjs:5470:5)
at async loadNuxt (node_modules/.pnpm/@nuxt+kit@3.15.1_magicast@0.3.5_rollup@4.30.0/node_modules/@nuxt/kit/dist/index.mjs:2640:19)
at async Object.run (node_modules/.pnpm/nuxi@3.18.2/node_modules/nuxi/dist/chunks/prepare.mjs:48:18)
at async runCommand$1 (node_modules/.pnpm/nuxi@3.18.2/node_modules/nuxi/dist/shared/nuxi.vClchuwn.mjs:1767:16)
at async runCommand$1 (node_modules/.pnpm/nuxi@3.18.2/node_modules/nuxi/dist/shared/nuxi.vClchuwn.mjs:1758:11)
at async runMain$1 (node_modules/.pnpm/nuxi@3.18.2/node_modules/nuxi/dist/shared/nuxi.vClchuwn.mjs:1896:7)
ERROR Cannot read properties of undefined (reading 'replace')
renovatebot
changed the title
chore(deps): update pnpm to v9.15.2
chore(deps): update pnpm to v9.15.3
Jan 6, 2025
renovatebot
changed the title
chore(deps): update pnpm to v9.15.7
chore(deps): update pnpm to v9.15.9
Mar 10, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
9.14.4+sha512.c8180b3fbe4e4bca02c94234717896b5529740a6cbadf19fa78254270403ea2f27d4e1d46a08a0f56c89b63dc8ebfd3ee53326da720273794e6200fcf0d184ab→9.15.9Release Notes
pnpm/pnpm (pnpm)
v9.15.9: pnpm 9.15.9Compare Source
Patch Changes
Platinum Sponsors
Gold Sponsors
v9.15.8: pnpm 9.15.8Compare Source
Patch Changes
pnpm self-updateshould always update the version in thepackageManagerfield ofpackage.json.--silentreporting is used.--loglevelis set toerror, don't show installation summary, execution time, and big tarball download progress.--loglevel=erroris used.Platinum Sponsors
Gold Sponsors
v9.15.7: pnpm 9.15.7Compare Source
Patch Changes
pnpm self-updateshould not leave a directory with a broken pnpm installation if the installation fails.--config.prefix such as--@​scope:registry=https://scope.example.com/npm#9089.pnpm self-updateshould not read the pnpm settings from thepackage.jsonfile in the current working directory.pnpm update -ishould list only packages that have newer versions #9206.catalogssection of thepnpm-lock.yamlfile to be removed whendedupe-peer-dependents=falseon a filtered install. #9112Platinum Sponsors
Gold Sponsors
v9.15.6: pnpm 9.15.6Compare Source
Patch Changes
packageManagercannot start withv.pnpm-lock.yamlfile when using--fix-lockfileand--filter. #8639v9.15.5: pnpm 9.15.5Compare Source
Patch Changes
pnpm install, thepreprepareandpostpreparescripts of the project should be executed #8989.strip-ansiwith the built-inutil.stripVTControlCharacters#9009.Platinum Sponsors
Gold Sponsors
v9.15.4: pnpm 9.15.4Compare Source
Patch Changes
pnpm update --latest <pkg>updates only the specified package, withdedupe-peer-dependents=true.Platinum Sponsors
Gold Sponsors
v9.15.3: pnpm 9.15.3Compare Source
Patch Changes
pnpm update --filter <pattern> --latest <pkg>should only change the specified package for the specified workspace, whendedupe-peer-dependentsis set totrue#8877..DS_Storefile atpatch-commit#8922.pnpm patchis unable to bring back old patch without specifying@versionsuffix #8919.Platinum Sponsors
Gold Sponsors
v9.15.2: pnpm 9.15.2Compare Source
Patch Changes
publish/packerror with workspace dependencies with relative paths #8904. It was broken inv9.4.0(398472c).pnpm patchon Windows #7546.git ls-remoteworks via HTTPS #8906.Platinum Sponsors
Gold Sponsors
v9.15.1: pnpm 9.15.1Compare Source
Patch Changes
pnpm removeshould not link dependencies from the workspace, whenlink-workspace-packagesis set tofalse#7674.node_modulesshould not fail, when a dependency has itself in its own peer dependencies #8854.Platinum Sponsors
Gold Sponsors
v9.15.0: pnpm 9.15Compare Source
Minor Changes
Patch Changes
pnpm update --globalshould not crash if there are no any global packages installed #7898.pnpm update --interactiveif catalogs are used.Platinum Sponsors
Gold Sponsors
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.